System and method to control wireless communications

ABSTRACT

Methods and systems to control wireless communications are provided. A particular network communication system includes a plurality of distributed mobile architecture gateways. Each distributed mobile architecture gateway includes at least one interface to communicate with one or more legacy communication networks and each distributed mobile architecture gateway also includes a data network connection. The data network connection is adapted to connect to at least one other distributed mobile architecture gateway of the plurality of distributed mobile architecture gateways. Additionally, the system includes a private Internet Protocol (IP) network connecting each distributed mobile architecture gateway to a respective set of distributed mobile architecture (DMA) servers. Each DMA server is coupled to a respective base transceiver station, and the private IP network also connects each DMA server in a particular set of DMA servers to the DMA servers in the other sets of DMA servers.

CLAIM OF PRIORITY

The present application claims priority from and is a continuation ofU.S. patent application Ser. No. 12/146,618, filed on Jun. 26, 2008 andentitled “SYSTEM AND METHOD TO CONTROL WIRELESS COMMUNICATIONS,” thecontents of which are expressly incorporated herein by reference intheir entirety.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to controlling wirelesscommunications.

BACKGROUND

Access to basic telephony service is particularly important for ruraland isolated communities. Telephony access allows small-scaleenterprises, cooperatives, and farmers to obtain accurate information onfair prices for their products and to access regional and nationalmarkets. Access also reduces the cost of transportation and supports thelocal tourist industry. By bringing markets to people viatelecommunications, rather than forcing people to leave in search ofmarkets, urban migration is reduced and greater income and employmentpotential are generated in rural areas.

Unfortunately, the last decade of the telecommunications boom has notalleviated the disparities between urban and rural communities. Theaverage imbalance, in terms of telephone penetration, in Asia, forexample, is over ten to one and is often as high as twenty to 1.2. Thismeans that a country whose urban markets have a penetration of four (4)telephone lines per one-hundred (100) inhabitants, e.g., India andPakistan, has a rural penetration of less than 0.2 per one-hundred(100). The situation is more acute in most African countries and in someparts of Latin America. By comparison, the disparity in average incomelevel between urban and rural residents in the developing world isusually less than 4 to 1.

Current telephone systems are expensive to deploy. For example, atypical cellular system that includes a mobile switching center (MSC), abase station controller (BSC), and a home location register/visitorlocation register (HLR/VLR) can cost over $2.0 million. Moreover, such asystem may require a minimum of ten thousand users in order to beeconomically viable. In many rural areas, the population is not largeenough to support the installation of such a system. Further, in manycases, the conditions in which the equipment, e.g., the MSC, BSC, andHLR/VLR, are to be operated are extremely harsh and environmentallychallenging. An alternative to such a cellular system can include awired system, but the costs associated with deploying and maintainingland lines are too high for certain rural areas.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an embodiment of a system to controlwireless communications;

FIG. 2 is a block diagram of a second embodiment of a system to controlwireless communications;

FIG. 3 is a block diagram of a third embodiment of a system to controlwireless communications;

FIG. 4 is a block diagram of a fourth embodiment of a system to controlwireless communications;

FIG. 5A illustrates an embodiment of a home distributed mobilearchitecture (DMA) server register utilized to control wirelesscommunications;

FIG. 5B illustrates an embodiment of a visitor distributed mobilearchitecture (DMA) server register utilized to control wirelesscommunications;

FIG. 5C illustrates an embodiment of a community distributed mobilearchitecture (DMA) server register utilized to control wirelesscommunications;

FIG. 6 is a flow diagram of a first embodiment of a method ofcontrolling wireless communications;

FIG. 7 is a flow diagram of a second embodiment of a method ofcontrolling wireless communications;

FIG. 8 is a is a block diagram of a fifth embodiment of a system tocontrol wireless communications;

FIG. 9 is a block diagram of a sixth embodiment of a system to controlwireless communications;

FIG. 10 is a block diagram of a seventh embodiment of a system tocontrol wireless communications;

FIG. 11 is a block diagram of an eighth embodiment of a system tocontrol wireless communications;

FIG. 12 is a block diagram of a ninth embodiment of a system to controlwireless communications; and

FIG. 13 is a block diagram of a tenth embodiment of a system to controlwireless communications.

DETAILED DESCRIPTION OF THE DRAWINGS

In a particular embodiment, a network communication system is disclosedthat includes a first distributed mobile architecture gateway (DMAG)having a first interface to communicate with a legacy communicationnetwork and a second interface to communicate with a private internetprotocol (IP) network. The first DMAG also has logic to forward voicetraffic received via the first interface to a first distributed mobilearchitecture (DMA) server via the private IP network. The voice trafficis directed to a wireless communication device associated with the firstDMA server and the first DMA server is one of a first plurality of DMAservers designated by a communications service provider to communicatevia the first DMAG. Additionally, the first DMAG includes a homedistributed mobile architecture server register comprising informationrelated to each of the plurality of DMA servers designated tocommunicate via the first DMAG and a visitor distributed mobilearchitecture server register including information related to visitorDMA servers that are temporarily registered with the first DMAG and thatare designated to communicate via at least a second DMAG.

In another embodiment, a network communication system is disclosed thatincludes a distributed mobile architecture (DMA) server coupled to abase transceiver station. The DMA server includes a routing moduleadapted to receive first voice traffic via a legacy communicationnetwork. The first voice traffic is directed to a wireless communicationdevice within a coverage area of the DMA server. The routing module isalso adapted to receive first signaling information related to the firstvoice traffic from a distributed mobile architecture gateway (DMAG) viaa private Internet Protocol (IP) network. Further, the routing module isadapted to route the first voice traffic to the wireless communicationdevice via the base transceiver station according to the first signalinginformation.

In another embodiment, a network communication system is disclosed thatincludes a plurality of distributed mobile architecture gateways. Eachdistributed mobile architecture gateway includes at least one interfaceto communicate with one or more legacy communication networks and eachdistributed mobile architecture gateway including a data networkconnection. The data network connection adapted to connect to at leastone other distributed mobile architecture gateway of the plurality ofdistributed mobile architecture gateways. The system also includes aprivate Internet Protocol (IP) network connecting each distributedmobile architecture gateway to a respective set of distributed mobilearchitecture (DMA) servers. Each DMA server is coupled to a respectivebase transceiver station, and the private IP network also connects eachDMA server in a particular set of DMA servers to the DMA servers in theother sets of DMA servers.

A method of routing calls via a communications network is disclosed thatincludes receiving a call at a first distributed mobile architecturegateway (DMAG) via a legacy communication network, where the voicetraffic is placed to a first wireless communication device. The methodalso includes identifying that the first wireless communication deviceis adapted to communicate via a first DMA server based on wirelesscommunication device registration data stored at the first DMAG. Thefirst DMA server is one of a plurality of DMA servers designated by acommunications service provider to communicate via the first DMAG.Further, the method includes routing the voice traffic from the firstDMAG to the first DMA server via a private Internet Protocol (IP)network.

In another embodiment, a method of routing calls via a communicationsnetwork is disclosed that includes receiving first voice traffic at afirst distributed mobile architecture (DMA) server from a first wirelesscommunication device via a base transceiver station integrated with thefirst DMA server. The first DMA server is adapted to receive the firstvoice traffic while being transported from a first location to a secondlocation. In addition, the method includes forwarding first packet datarelated to the first voice traffic over a private internet protocol (IP)network to a distributed mobile architecture gateway (DMAG), where thefirst voice traffic is directed to a destination device that isaccessible via a legacy communication network.

Referring to FIG. 1, a system to control wireless communications isshown and is generally designated 100. The system 100 includes one ormore legacy networks 102 coupled to a distributed mobile architecturegateway (DMAG) 104. The one or more legacy networks 102 may include oneor more wide-area wireless communication networks, one or more landlinecommunication networks, one or more local area networks (LANs), one ormore wireless local area networks (WLANs), or any combination thereof.In an illustrative, embodiment, one or more wide-area wirelesscommunication networks may carry voice traffic 104, data traffic 106, orany combination thereof. For example, the wireless voice traffic 104 maybe carried over a Global System for Mobile Communications (GSM) network,a Code Division Multiple Access (CDMA) network, a Time Division MultipleAccess (TDMA) network, a Universal Mobile Telecommunications System(UMTS) network, a Personal Communications Service (PCS) network, or anycombination thereof. Signaling related to the wireless voice traffic 104may be carried over a Signaling System 7 (SS7) network and utilize anAmerican National Standards Institute (ANSI) 41 protocol, a MobileApplication Part (MAP) protocol, or a Customized Application of MobileEnhanced Logic (CAMEL) protocol. The wireless data traffic 106 may becarried over a General Packet Radio Service (GPRS) network, an enhancedGPRS (EGPRS) network, an IEEE 802.16 network, a UMTS network, a HighSpeed Packet Access (HSPA) network, or any combination thereof. Thewireless data traffic 106 may be formatted according to InternetProtocol (IP). Additionally, wireless voice traffic may be carried overa wireless data traffic connection 104 using a mobile Voice overInternet Protocol (VoIP) technology.

One or more landline communication networks may carry voice traffic 108,data traffic 110, or any combination thereof. The one or more landlinecommunication networks may carry landline voice traffic 108 over aPublic Switched Telephone Network (PSTN), an Integrated Services DigitalNetwork (ISDN), or any combination thereof. Signaling related to thelandline voice traffic 108 may be carried over an SS7 network andutilize an Integrated Service Digital Network User Part (ISUP) protocol.The landline data traffic 110 may be carried over a Digital SubscriberLine (DSL) network, an Asynchronous Transfer Mode (ATM) network, anoptical fiber network, a coaxial cable network, or any combinationthereof. Landline voice traffic may also be carried over a landline datatraffic connection 110 using Voice over Internet Protocol (VoIP). Thelandline data traffic 110 may also be formatted according to InternetProtocol (IP).

The legacy networks 102 communicate the wireless voice traffic 104, thewireless data traffic 106, the landline voice traffic 108, the landlinedata traffic 110, or any combination thereof, to the DMAG 112. The DMAG112 is adapted to route voice traffic and data traffic between the oneor more legacy networks 102 and one or more wireless communicationdevices, such as the wireless communication devices 122, 124 via aprivate Internet Protocol (IP) network 114. The private IP network 114may include a landline IP network, a wireless IP network, or anycombination thereof.

The DMAG 112 routes voice traffic and data traffic between the one ormore legacy networks 102 and one or more wireless communication devicesvia one or more distributed mobile architecture (DMA) servers, such asthe first DMA server 116, the second DMA server 118, and the third DMAserver 120. For example, the DMAG 112 may route voice traffic and datatraffic between the one or more legacy networks 102 and the firstwireless communication device 122 and the second wireless communicationdevice 124 via the second DMA server 118. The DMAG 112 may also routevoice traffic and data traffic between the one or more legacy networks102 and the third wireless communication device 126 via the third DMAserver 120.

Additionally, the DMAG 112 may route voice traffic and data trafficbetween the wireless communication devices 122-126. For example, theDMAG 112 may route voice traffic and data traffic between wirelesscommunication devices served by the same DMA server. To illustrate, theDMAG 112 may route voice traffic and data traffic between the firstwireless communication device 122 and the second wireless communicationdevice 124. Further, the DMAG 112 may route voice traffic and datatraffic between wireless communication devices served by different DMAservers. In an illustrative example, the DMAG 112 may route voicetraffic and data traffic between the first wireless communication device122 and the third wireless communication device 126.

In a particular embodiment, the DMAG 112 may be associated with aservice area 130. The DMAG 130 may control communications of DMA serverslocated within the service area 130, such as the DMA servers 116-120.The service area 130 may include one or more wireless connections, oneor more wireline connections, or any combination thereof, between the IPnetwork 114 and the DMAG 112, between the DMA servers 116-120 and theDMAG 112, or any combination thereof. Although the service area 130 isshown in FIG. 1 with a particular shape and a particular size, theservice area 130 may be a different shape and a different size than theshape and size shown in FIG. 1.

In an illustrative embodiment, a communications service provider mayspecify that the DMAG 112 is assigned as a primary DMAG to route voicetraffic, data traffic, or any combination thereof, related to designatedDMA servers. The designated DMA servers may be located within theservice area 130 of the DMAG 112 at a given time or the designated DMAservers may be located outside of the service area 130 at a given time.Additionally, the DMAG 112 may route voice traffic, data traffic, or anycombination thereof, related to DMA servers that have roamed into thecoverage area 130. A particular DMA server may be considered roamingwith respect to the DMAG 112 when an additional DMAG (not shown) isdesignated as the primary node to route communications related to theparticular DMA server and the particular DMA server moves out of thecoverage area of the additional DMAG and into the coverage area 130 ofthe DMAG 112. For example, the DMAG 112 may serve as the primary node toroute communications related to the first DMA server 116 and the secondDMA server 118, while the third DMAG 120 has roamed into the coveragearea 130.

Each of the DMA servers 116-120 are adapted to route voice traffic, datatraffic, or any combination thereof, related to wireless communicationdevices served by the respective DMA server. For example, the DMAservers 116-120 may be adapted to route voice traffic and data trafficbetween wireless communication devices served by the same DMA server. Toillustrate, the second DMA server 118 may route voice traffic and datatraffic between the first wireless communication device 122 and thesecond wireless communication device 124. Additionally, the DMA servers116-120 may be adapted to route voice traffic and data traffic betweenwireless communication devices served by different DMA servers. In anexample, the second DMA server 118 and the third DMA server 120 mayroute voice traffic and data traffic between the first wirelesscommunication device 122 and the third wireless communication device126.

In a particular embodiment, the second DMA server 118 may be associatedwith a service area 132 and the second DMA server 118 may routecommunications associated with wireless communication devices locatedwithin the service area 132, such as the wireless communication devices122, 124. The service area 132 may include one or more wirelessconnections to the wireless communication devices 122, 124, such as along range wireless connection or a short range wireless connection.Although the service area 132 is shown in FIG. 1 with a particular shapeand a particular size, the service area 132 may be a different shape anda different size than the shape and size shown in FIG. 1.

A communications service provider may specify that each of the DMAservers 116-120 may be assigned to serve as a primary DMA server forrouting communications related to designated wireless communicationdevices. For example, the second DMA server 118 may serve as the primaryDMA server for the first wireless communication device 122. The firstwireless communication device 122 may be located within the service area132 of the second DMA server 118 at a given time or the first wirelesscommunication device 122 may be located outside of the service area 132at a given time. Additionally, the second DMA server 118 may route voicetraffic, data traffic, or any combination thereof, related to wirelesscommunication devices that have roamed into the coverage area 132. Aparticular wireless communication device, such as the second wirelesscommunication device 124, may be considered roaming with respect to thesecond DMA server 118 when an additional DMA server, such as the firstDMA server 116, is designated as the primary node to routecommunications related to the particular wireless communication deviceand the particular wireless communication device moves out of thecoverage area of the additional DMA server and into the coverage area132 of the second DMA server 118.

Each of the DMA servers 116-120 may be adapted to send and receivecommunications related to wireless communication devices within therespective coverage area of the particular DMA server via one or morebase transceiver stations (not shown) coupled to the particular DMAserver. A particular DMA server may be coupled to a base transceiverstation via a wireline connection or a wireless connection.Additionally, the one or more base transceiver stations may be coupledto one or more antennas (not shown), such as a directional antenna.

Referring to FIG. 2, a second embodiment of a system to control wirelesscommunications is illustrated and generally designated 200. The system200 includes distributed mobile architecture gateways (DMAGs) 202-206.Each of the DMAGs 202-206 is coupled to one or more legacy networks. Forexample, the first DMAG 202 is coupled to one or more legacy networks208, the second DMAG 204 is coupled to one or more legacy networks 210,and the third DMAG 206 is coupled to one or more legacy networks 212.Each of the legacy networks 208-212 may include one or more landlinenetworks, one or more wireless networks, or any combination thereof, tocarry voice traffic and/or data traffic to the DMAGs 202-206. Althoughthe legacy networks 208-212 are shown as separate boxes, the legacynetworks 208-212 may include one or more of the same legacy networks.Alternatively, each of the DMAGs 202-208 may serve as a backhaul todifferent legacy networks. To illustrate, the one or more legacynetworks 208 may include legacy landline voice and data networks, theone or more legacy networks 210 may include a particular wireless voiceand data network, such as a time division multiple access (TDMA)network, and the one or more legacy networks 212 may include anotherwireless voice and data network, such as a code division multiple access(CDMA) network.

Each of the DMAGs 202-206 may communicate via a private InternetProtocol (IP) network, such as the private IP networks 214-218. TheDMAGs 202-206 may communicate with each other via the private IPnetworks 214-218, with one or more groups of distributed mobilearchitecture (DMA) servers 220-224, or any combination thereof. Althoughthe private IP networks 214-218 are shown in FIG. 2 as separatenetworks, the private IP networks may represent either separate privateIP networks or a single private IP network.

In a particular embodiment, the first DMAG 202 controls communicationsrelated to the first group of DMA servers 220 via the first private IPnetwork 214. Additionally, the second DMAG 204 controls communicationsrelated to the second group of DMA servers 222 via the second private IPnetwork 216 and the third DMAG 206 control communications related to thethird group of DMA servers 224 via the third private IP network 218.Each of the DMA servers in a respective group of DMA servers maycommunicate with one or more wireless communication devices (not shown).

Each of the DMAGs 202-206 may control communications related to arespective group of DMA servers by routing voice traffic, data traffic,signaling, or any combination thereof, between the one or more legacynetworks 208-212 and one or more wireless communication devicescommunicating with the respective groups of DMA servers 220-224. In anillustrative embodiment, the second DMAG 204 may be adapted to controlcommunications related to the second group of DMA servers 222 by routingvoice traffic, data traffic, signaling, or any combination thereof,between the one or more legacy networks 210 and one or more wirelesscommunication devices registered with the DMA servers 230-236.

In an illustrative embodiment, each DMAG 202-206 may be specified by acommunications service provider as a primary node to control voicetraffic, data traffic, signaling, or any combination thereof, fordesignated DMA servers. For example, the second DMAG 204 may serve as aprimary node to control voice traffic, data traffic, signaling, or anycombination thereof, related to one or more of the DMA servers of thesecond group of DMA servers 222, such as the DMA servers 230-232.Additionally, the second DMAG 204 may control voice traffic, datatraffic, signaling, or any combination thereof, related to one or moreof the DMA servers of the second group of DMA servers 222 that haveroamed into a coverage area associated with the second DMAG 204, such asthe DMA servers 234-236.

Each DMA server of a particular group of DMA servers may be specified asa primary node for controlling communications related to one or moredesignated wireless communication devices. In addition, each DMA serverof a particular group of DMA servers may be adapted to controlcommunications related to one or more wireless communication devicesthat have roamed into a coverage area of a particular DMA server.Wireless communication devices may roam between DMA servers within aparticular group of DMA servers and wireless communication devices mayroam between DMA servers included in different groups of DMA servers. Inone example, when the DMA server 230 serves as a primary node for aparticular wireless communication device, the particular wirelesscommunication device can roam from the coverage area of the DMA server230 to a coverage area of the DMA server 232. In another example, whenthe DMA server 230 serves as a primary node for a particular wirelesscommunication device, the particular wireless communication device canroam into a coverage area of a DMA server of the third group of DMAservers 224.

In an illustrative embodiment, a DMA server, such as the DMA server 230may move from one group of DMA servers, such as the second group of DMAservers 222, to another group of DMA servers, while controllingcommunications related to one or more wireless communication devices inthe coverage area of the DMA server 230. In an example, one or morewireless communications devices in the coverage area of the DMA server230 when the DMA server 230 is included in the second group of DMAservers 222 may remain within the coverage area the DMA server 230 bymoving along with the DMA server 230 to the third group of DMA servers224. Further, as the DMA server 230 moves to the third group of DMAservers 224, one or more additional wireless communication devices mayregister with the DMA server 230. In an illustrative, non-limitingembodiment, the second group of DMA servers 222 may be associated with acoverage area of the second DMAG 204 and the third group of DMA servers224 may be associated with a coverage area of the third DMAG 206.

Each particular DMAG 202-206 may be adapted to route communications,between wireless communication devices in coverage areas of differentDMA servers of the respective group of DMA servers associated with theparticular DMAG. Additionally, each DMAG 202-206 may be adapted to routecommunications between wireless communication devices in the coveragearea of the same DMA server of the respective group of DMA serversassociated with the particular DMAG. In one example, the second DMAG 204may be adapted to route voice traffic, data traffic, or any combinationthereof, between wireless communication devices in the coverage area ofthe DMA server 230 and wireless communication devices in the coveragearea of the DMA server 232. In another example, the second DMAG 204 maybe adapted to route voice traffic, data traffic, or any combinationthereof, between wireless communication devices in the coverage area ofthe DMA server 230. Further, the DMAGs 202-206 may be adapted to controlcommunications between wireless communication devices in the coveragearea of a DMA server of one group of DMA servers and in the coveragearea of another DMA server of a different group of DMA servers. Toillustrate, the second DMAG 204 and the third DMAG 206 may be adapted toroute voice traffic, data traffic, or any combination thereof, between awireless communication device in the coverage area of the DMA server 230and a wireless communication device in the coverage area of a DMA serverof the third group of DMA servers 224.

In addition, each DMA server of a particular group of DMA servers may beadapted to route communications locally between wireless communicationdevices in the coverage area of the respective DMA server. For example,the DMA server 230 may be adapted to control voice traffic, datatraffic, or any combination thereof, related to one or more wirelesscommunication devices in the coverage area of the DMA server 230.Further, DMA servers included in a particular group of DMA servers maybe adapted to route communications between wireless communicationdevices in the coverage areas of the DMA servers of the same group ofDMA servers. To illustrate, the DMA server 230 and the DMA server 232may be adapted to control voice traffic, data traffic, or anycombination thereof, between wireless communication devices in thecoverage area of the DMA server 230 and wireless communication devicesin the coverage area of the DMA server 232. Additionally, DMA serversincluded in different groups of DMA servers may be adapted to routecommunications between wireless communication devices in coverage areasof the DMA servers included in the different groups. In an example, theDMA server 230 and a particular DMA server of the third group of DMAservers 224 may control voice traffic, data traffic, or any combinationthereof, between wireless communication devices in the coverage area ofthe DMA server 230 and wireless communication devices in the coveragearea of the particular DMA server included in the third group of DMAservers 224.

In the event of a failure of a particular DMAG, one or more DMAGs maycontrol communications that would otherwise be controlled by the failedDMAG. In an illustrative embodiment, in the event of a failure of thesecond DMAG 204, the first DMAG 202, the third DMAG 206, or anycombination thereof, may control communications related to the secondgroup of DMA servers 222. For example, the first DMAG 202 and the thirdDMAG 207 may control voice traffic, data traffic, signaling, or anycombination thereof, between the one or more legacy networks 210 and thewireless communication devices in the coverage areas the DMA servers230-236.

Each of the DMAGs 202-206 may include redundant registration data withrespect to each other, in order to assume control of communications inresponse to a failure in another one of the DMAGs 202-206. Theregistration data related to a particular DMAG may be redundantly storedin one or more additional DMAGs. In an illustrative, non-limitingembodiment, redundant registration data related to the second DMAG 204may be stored at the first DMAG 202 and the third DMAG 206.

Registration data may identify that a particular DMAG is specified asthe primary node to control communications related to certain DMAservers. In addition, registration data may identify a number of DMAservers that are roaming with respect to a particular DMAG. For example,registration data associated with the second DMAG 204 may identify thatthe second DMAG 204 is the primary node for the DMA servers 230-232 andthat the DMA servers 234-236 are roaming with respect to the DMAG 204.Further, registration data may identify the wireless communicationdevices that are registered with the DMA servers included in aparticular group of DMA servers. To illustrate, registration dataassociated with the second DMAG 204 may identify that the DMA server 230is specified to serve as a primary node to control communicationsrelated to some wireless communication devices registered with the DMAserver 230 and that other wireless communication devices registered withthe DMA server 230 are roaming with respect to the DMA server 230.Registration data related to a particular wireless communication devicemay include an identifier, such as an international mobile subscriberidentification (IMSI), associated with the particular wirelesscommunication device. Additionally, the registration data may includefurther information related to an account associated with a particularwireless communication device.

Additionally, the DMA servers within a particular group of DMA serversmay include redundant registration data needed to route communicationsin response to a failure of a DMA server in the particular group of DMAservers. In an illustrative embodiment, each DMA server of the secondgroup of DMA servers 222 includes registration data identifying one ormore wireless communication devices registered with one or more of theother DMA servers in the second group of DMA servers 222. For example,the DMA server 230 may include registration data identifying wirelesscommunication devices in the coverage area of the DMA server 230 andregistration data identifying wireless communication devices in thecoverage area of the DMA server 232 and in the coverage area of the DMAserver 234. Thus, the DMA server 230 can route voice traffic, datatraffic, or any combination thereof, of wireless communication devicesin the respective coverage areas of the DMA servers 232, 234, if the DMAserver 232 and/or the DMA server 234 fails. To illustrate, if the DMAserver 232 fails, the DMA server 230 can route communications betweenthe second DMAG 204 and the wireless communication devices in thecoverage area of the failed DMA server 232. Additionally, the DMA server230 can route communications between wireless communication devices inthe coverage area of the DMA server 232 at the time of failure. Further,the DMA server 230 can route communications between wirelesscommunication devices in the coverage area of the DMA server 232 andwireless communication devices in the coverage area of other DMA serversof the system 200.

In some embodiments, a communications service provider may specify thatone or more of the DMAGs 202-206 are adapted to route voice traffic,data traffic, and signaling related to wireless communication devicesserved by a particular group of DMA servers. In other embodiments, acommunications service provider may specify that a particular DMAG isadapted to route voice and data traffic related to wirelesscommunications devices served by a particular group of DMA servers,while another DMAG is adapted to handle the signaling related tocommunications associated with wireless communication devices registeredwith the particular group of DMA servers. In an example, the first DMAG202 may be adapted to manage signaling related to communicationsassociated with each group of DMA servers 220-224, while the second DMAG204 and the third DMAG 206 are adapted to control voice traffic and datatraffic related to communications associated with each group of DMAservers 220-224.

Referring to FIG. 3, a third embodiment of a system to control wirelesscommunications is illustrated and generally designated 300. The system300 includes one or more legacy networks 302, such as one or morelandline communication networks, one or more wireless communicationnetworks, or any combination thereof. The legacy networks 302 maycommunicate voice traffic, data traffic, signaling, or any combinationthereof, with one or more distributed mobile architecture gateways(DMAGs) 304, 306, one or more distributed mobile architecture (DMA)servers 310-318, or any combination thereof. Each of the DMAGs 304, 306may be designated to control communications related to one or moredistributed mobile architecture (DMA) servers. For example, the firstDMAG 304 may be designated by a communications service provider tocontrol communications related to the first DMA 310, the second DMA 312,and the third DMA 314. Additionally, the second DMAG 306 may bedesignated to control communications related to the fourth DMA 316 andthe fifth DMA 318. The DMA servers 310-318 communicate with the DMAGs304, 306 via a private Internet Protocol (IP) network 308 and the DMAservers 310-318 communicate with each other via the private IP network308. Additionally, the first DMAG 304 and the second DMAG 306communicate with each other via the private IP network 308.

Each of the DMA servers 310-318 may route communications related to oneor more wireless communication devices. To illustrate, the third DMAserver 314 may control voice traffic, data traffic, or any combinationthereof, related to the wireless communication devices 320, 322. Thevoice traffic and/or data traffic may be associated with the one or morelegacy networks 302, a wireless communication device associated withanother one of the DMA servers 310, 312, 316, 318, or another wirelesscommunication device associated with the third DMA server 314.

In an illustrative embodiment, the DMAGs 304, 306 may manage voicetraffic, data traffic, and signaling related to some of the DMA serversof the system 300, while managing only signaling traffic to other DMAservers of the system 300. For example, the DMAGs 304, 306 may beadapted to manage voice traffic, data traffic, and signaling for thesecond DMA server 312, the third DMA server 314, and the fourth DMAserver 316. In addition, the DMAGs 304, 306 may manage signaling relatedto the first DMA server 310 and the fifth DMA server 318. Voice trafficand data traffic related to the first DMA server 310 and the fifth DMAserver 318 may be communicated directly between the first DMA server 310and the fifth DMA server 318 and the legacy communication networks 302.Further, when one or more of the DMAGs 304, 306 fail, the first DMAserver 310 and the fifth DMA server 318 may be adapted to provide voicetraffic, data traffic, signaling, or any combination thereof, betweenthe DMA servers 312-316 and the one or more legacy networks 302. In anillustrative, non-limiting embodiment, the DMA servers 310, 318 may beresponsible for controlling all of the voice traffic and data trafficbetween the DMA servers 310-318 and the one or more legacy networks 302,while the DMAGs 304, 306 are responsible for controlling the signalingassociated with the voice traffic and the data traffic between the DMAservers 310-318 and the of more legacy networks.

Referring to FIG. 4, a fourth embodiment of a system to control wirelesscommunications is illustrated and is generally designated 400. Thesystem 400 includes a distributed mobile architecture gateway (DMAG) 402that communicates with a distributed mobile architecture (DMA) server404 via a private Internet Protocol (IP) network 406. The system 400also includes an additional DMA server 470 that is adapted tocommunicate with the DMAG 402, the DMA server 404, or any combinationthereof, via the private IP network 406.

The DMAG 402 includes a processor 408, a memory 410, and a data networkconnection 412 coupled to the private IP network 406. Additionally, theDMAG 402 includes a first network interface 414, a second networkinterface 416, a third network interface 418, and a fourth networkinterface 420. The first network interface 414 is adapted to communicatewith a landline voice network 422, such as a Public Switched TelephoneNetwork (PSTN), an Integrated Services Digital Network (ISDN), or anycombination thereof. The second network interface 416 is adapted tocommunicate with a landline data network 424, such as a DigitalSubscriber Line (DSL) network, a cable television network, or anycombination thereof. The third network interface 418 is adapted tocommunicate with a wireless voice network 426, such as a Global Systemfor Mobile Communications (GSM) network, a Code Division Multiple Access(CDMA) network, a Time Division Multiple Access (TDMA) network, or anycombination thereof. The fourth network interface 420 is adapted tocommunicate with a wireless data network 428, such as a General PacketRadio Service (GPRS) network, an IEEE 802.16 network, a UMTS network, aHigh Speed Packet Access (HSPA) network, or any combination thereof.

Signaling received via the first network interface 414 from the landlinevoice network 422 may relate to Intelligent Network (IN) signaling, suchas Signaling System 7 (SS7), and include Integrated Services DigitalNetwork User Part (ISUP) signaling, Message Transfer Part (MTP)signaling, Signaling Control Connection Part (SCCP) signaling,Transaction Capabilities Application Part (TCAP) signaling, TelephoneUser Part (TUP) signaling, Data User Part (DUP) signaling, or anycombination thereof. Further, signaling received via the second networkinterface 414 from the landline data network 424 related to Voice overInternet Protocol (VoIP) traffic may include session initiation protocol(SIP) signaling, H.323 signaling, or any combination thereof.Additionally, signaling received via the third network interface 418from the wireless voice network 426 may relate to IN signaling and beformatted according to mobile application part (MAP) protocol, AmericanNational Standards Institute (ANSI) 41 protocol, customized applicationof mobile enhanced logic (CAMEL) protocol, or any combination thereof.Signaling received via the fourth network interface 420 from thewireless data network 428 related to VoIP traffic may include SIPsignaling.

Although the landline voice network 422 and the landline data network424 are shown coupled to separate network interfaces 414 and 416,respectively, the landline voice network 422 and the landline datanetwork 424 may utilize the same infrastructure and be coupled to asingle interface. In an illustrative embodiment, the landline voicenetwork 422 and the landline data network 424 may be related to atelephone company communications network that carries voice traffic viaa circuit switched PSTN and data traffic via a packet switched DSLnetwork. The DMAG 402 may receive voice traffic and the data trafficfrom the telephone company communications network at a single interfacethat separates the voice traffic, the data traffic, signalinginformation, or any combination thereof.

Further, although the wireless voice network 426 and the wireless datanetwork 428 are shown coupled to separate network interfaces 418, 420,respectively, the wireless voice network 426 and the wireless datanetwork 428 may utilize the same infrastructure and be coupled to asingle interface. In an illustrative embodiment, the wireless voicenetwork 426 and the wireless data network 428 may be related to awireless communications provider network that carries voice traffic viaa Global System for Mobile Communications (GSM) network and carries datatraffic via a General Packet Radio Service (GPRS) network. The DMAG 402may receive voice traffic and data traffic from the wirelesscommunications provider network at a single interface that separates thevoice traffic, the data traffic, signaling information, or anycombination thereof.

The memory 410 includes a coverage module, one or more gateway modules432, one or more conversion modules 434, and a routing module 436. Inone embodiment, each of the modules 430-436 can represent instructionsthat are executable by the processor 408, such as instructions embodiedin one or more software programs stored at the memory 410. In anotherembodiment, the modules 430-436 can represent hardware, softwareinstructions, or any combination thereof.

The DMAG 402 also includes a register data store 438. The register datastore 438 may include one or more databases storing information relatedto one or more DMA servers. For example, the register data store 438 mayinclude a home DMA server register of the DMAG 402. The home DMA serverregister of the DMAG 402 may include register information related to oneor more DMA servers that are designated by a communications serviceprovider to send and receive communications via the DMAG 402 as theprimary node. The register information for a particular DMA server mayinclude an identifier, such as an IP address, other routing dataassociated with the particular DMA server, connectivity data indicatingthat the particular DMA server is within a coverage area of a particularDMAG, data indicating that the particular DMA server is offline, or anycombination thereof.

The register data store 438 may also include a visitor DMA serverregister that includes registration information related to DMA serversthat have roamed into the coverage area of the DMAG 402. Further, theregister data store 438 may include one or more community DMA registers.The one or more community DMA registers may include one or more home DMAserver registers and one or visitor DMA server registers of additionalDMAGs that are adapted to communicate with the DMAG 402. Examples of thestructure of data stores including the register data 436 are shown inFIG. 5 and FIG. 6.

Further, the register data store 438 may include information related towireless communication devices registered with the DMA serversassociated with the DMAG 402. For example, the register data store 438may include a respective home location register (HLR) associated witheach DMA server in the home DMA server register of the DMAG 402, eachDMA server in the visitor DMA server register of the DMAG 402, each DMAserver in the one or more community DMA registers of the DMAG 402, orany combination thereof. In an illustrative embodiment, the registerdata store 438 may include an HLR associated with the DMA server 404.The HLR of the DMA server 404 may include wireless communication deviceregistration information related to one or more wireless communicationdevices that a communications service provider has designated to sendand receive voice traffic and/or data traffic via the DMA server 404 asthe primary node. The wireless communication device registrationinformation may include an identifier associated with each respectivewireless communication device, such as an international mobilesubscriber identification (IMSI). Additionally, the wirelesscommunication device registration information may include other routingdata associated with the respective wireless communication device,connectivity data indicating that the respective wireless communicationdevice is within a coverage area of a particular DMA server, dataindicating that the respective wireless communication device is within acoverage area of a legacy network, or any combination thereof.

Further, the register data store 438 may include a respective visitorlocation register (VLR) associated with each DMA server in the home DMAserver register of the DMAG 402, each DMA server in the visitor DMAserver register of the DMAG 402, each DMA server in the one or morecommunity DMA registers of the DMAG 402, or any combination thereof. Inan illustrative embodiment, the register data store 438 may include aVLR associated with the DMA server 404. The VLR of the DMA server 404may include wireless communication device registration informationrelated to one or more wireless communication devices that have roamedinto the coverage area of the DMA server 404. The wireless communicationdevices included in the VLR of the DMA server 404 have been designatedby a communications service provider to send and receive voice trafficand/or data traffic via a DMA server other than the DMA server 404, suchas the additional DMA server 470, as the primary node.

Further, the register data store 438 may include one or more communitylocation registers (CLRs) associated with each DMA server in the homeDMA server register of the DMAG 402, each DMA server in the visitor DMAserver register of the DMAG 402, each DMA server in the one or morecommunity DMA registers of the DMAG 402, or any combination thereof. Inan illustrative embodiment, the register data store 438 may include oneor more CLRs associated with the DMA server 404. The one or more CLRs ofthe DMA server 404 may include wireless communication deviceregistration information related to one or more wireless communicationdevices that are included in a home location register of a DMA serverother than the DMA server 404, such as the additional DMA server 470.Examples of data structures included in the register data store 438 areshown in FIG. 5 and FIG. 6.

The coverage module 430 is adapted to identify one or more DMA serversthat are located within a coverage area associated with the DMAG 402.The DMAG 402 may connect with a particular DMA server in the coveragearea of the DMAG 402 via a wireless connection, a wireline connection,or any combination thereof, via the private IP network 406. In oneembodiment, the coverage module 430 may identify that a particularcomputing device has connected to the DMAG 402 via a wirelineconnection, such as via a Universal Serial Bus (USB) port, andsubsequently receive identification information, such as an InternetProtocol address, from the computing device. The coverage module 430 maydetermine that the identification information indicates that theparticular computing device is a DMA server. For example, the coveragemodule 430 may compare the identification information received from theparticular computing device with DMA identification information in theregister data store 436. To illustrate, the DMA server 404 may send theDMAG 402 an IP address assigned to the DMA server 404 and the coveragemodule 430 is adapted to search a home DMA server register stored in theregister data store 438, a visitor DMA server register stored in theregister data store 438, one more community DMA registers stored in theregister data store 438, or any combination thereof, for the IP addressreceived from the DMA server 404.

In another embodiment, the coverage module 430 may be adapted toidentify that a particular computing device has connected to the DMAG402 via a wireless connection, such as a wide area wireless connectionor a local area wireless connection. In one example, the coverage module430 may be adapted to transmit identification signals, such as alocation update request via a wireless transceiver (not shown). Theidentification signals may be adapted to prompt a response in specifieddevices receiving the identification signals to send identificationinformation to the DMAG 402. In another example, the coverage module 430may be adapted to wirelessly receive identification information fromcomputing devices in the coverage area of the DMAG 402 without sendingthe identification signals. The coverage module 430 may determine thatidentification information received from the particular computing deviceindicates that the particular computing device is a DMA server. Thecoverage area of the DMAG 402 may be related to the strength of theidentification signals sent from the DMAG 402, the strength ofidentification information signals received from a computing device, orany combination thereof.

After determining that the DMAG 402 is connected to a particular DMAserver, the coverage module 430 may be adapted to register theparticular DMA server with the DMAG 402. The coverage module 430 mayregister the particular DMA server with the DMAG 402 by storing anindication in the register data store 438 specifying that the DMAG 402is adapted to route voice traffic, data traffic, signaling, or anycombination thereof, related to the particular DMA server. The coveragemodule 430 may store the indication in a home DMA server register of theregister data store 438 when a communications service provider hasspecified that the DMAG 402 is the primary node for routingcommunications related to the particular DMA server. The coverage module430 may store the indication in a visitor DMA server register of theregister data store 438 when the particular DMA server has roamed intothe coverage area of the DMAG 402.

In an illustrative embodiment, the coverage module 430 transmits anidentification signal and, in response, receives identificationinformation, such as an IP address, from the DMA server 404. Thecoverage module 430 may be adapted to establish a connection with theDMA server 404 and the coverage module 430 may be adapted to compare theIP address received from the DMA server 404 with information included inthe register data store 438. For example, the coverage module 430 maysearch a home DMA server register included in the register data store438. If the IP address of the DMA server 404 is not included in the homeDMA server register of the DMAG 404, the coverage module 430 may beadapted to update a visitor DMA server register included in the registerdata store 438. The coverage module 430 may be adapted to update thevisitor DMA server register by adding the IP address of the DMA server404 to the visitor DMA server register. Additionally, if the IP addressof the DMA server 404 is not included in the home DMA server register ofthe DMAG 404, the coverage module 404 may be adapted to search one ormore community DMA registers included in the register data store 438 toidentify the additional DMAG that is designated to route communicationsrelated to the DMA server 404. The coverage module 430 may also beadapted to send data to the additional DMAG indicating that the DMAserver 404 is within the coverage area of the DMAG 402. When the IPaddress of the DMA server 404 is included in a community

The one or more gateway modules 432 may be adapted to distribute voicetraffic, data traffic, signaling, or any combination thereof, receivedvia the network interfaces 414-420. In a particular embodiment, each ofthe network interfaces 414-420 may be associated with a respectivegateway module 432. For example, a first gateway module may be adaptedto receive voice traffic, signaling, or any combination thereof, fromthe first network interface 414. The first gateway module may send voicetraffic to a corresponding conversion module 434 and send signaling tothe routing module 436. Additionally, a second gateway module may beadapted to receive voice traffic, data traffic, signaling, or anycombination thereof, from the second network interface 416. The secondgateway module may send voice traffic and data traffic to acorresponding conversion module 434 and send signaling to the routingmodule 436. Further, a third gateway module may be adapted to receivevoice traffic, signaling, or any combination thereof, from the thirdnetwork interface 418. The third gateway module may send the voicetraffic to a corresponding conversion module 434 and send signaling tothe routing module 436. The one or more gateway modules 432 may alsoinclude a fourth gateway module adapted to receive voice traffic, datatraffic, signaling, or any combination thereof, via the fourth networkinterface 420. The fourth gateway module may send voice traffic and datatraffic to corresponding conversion modules 434 and send signaling tothe routing module 436.

Additionally, the one or more gateway modules 432 may be adapted toreceive voice traffic, data traffic, signaling, or any combinationthereof, via the data network connection 412, the one or more conversionmodules 434, the routing module 436, or any combination thereof. Thevoice traffic and/or data traffic received at the one or more gatewaymodules 432 may be intended for a destination device related to thelegacy networks 422-428. The one or more gateway modules 432 mayidentify a particular legacy network that can be utilized to send voicetraffic, data traffic, or any combination thereof, to the destinationdevice and route the voice traffic and/or data traffic to the identifiedlegacy network via the corresponding network interface. For example,when a destination device includes a landline telephone, the one or moregateway modules 432 may be adapted to route voice traffic intended forthe landline telephone via the first network interface 414.

The one or more conversion modules 432 may be adapted to convert voicetraffic, data traffic, or any combination thereof, received via thenetwork interfaces 414-420 to Internet Protocol (IP) for transmission toa destination wireless communication device via the private IP network406. In addition, the one or more conversion modules 432 may also beadapted to convert voice traffic, data traffic, or any combinationthereof, received via the data network connection 412 from IP to anotherformat that is appropriate for a legacy network associated with adestination device related to the voice and/or data traffic. In oneexample, the one or more conversion modules 432 may include a landlinevoice network conversion module that is adapted to convert IP datareceived via the data network connection 412 to a circuit switchedanalog format that can be transmitted via the landline voice network422, such as a Public Switched Telephone Network (PSTN). The landlinevoice network conversion module may also be adapted to convert circuitswitched analog data received via the first network interface 414 to IPdata. Further, the landline voice network conversion module may compressthe IP data associated with the received circuit switched analog databefore sending the IP data via the data network connection 412.

Additionally, the one or more conversion modules 432 may include alandline data network conversion module that is adapted to compress IPdata received via the second network interface 416. The landline datanetwork conversion module may also decompress IP data received from thedata network connection 414 before forwarding the received IP data to adestination device via the second network interface 416. The one or moreconversion modules 432 may also include a wireless voice networkconversion module that is adapted to convert IP data received via thedata network connection 414 to a format that can be transmitted via thewireless voice network 426. For example, the wireless voice networkconversion module may convert IP data related to voice traffic receivedvia the data network connection 414 according to Code Division MultipleAccess (CDMA), so that the voice traffic can be transmitted to adestination device via the wireless voice network 426. Further, thewireless voice network conversion module may convert voice trafficreceived via the third network interface 418 to IP for transmission viathe data network connection 414.

The wireless voice network conversion module may utilize an EnhancedVariable Rate Vocoder (EVRC) to compress voice traffic received via aCDMA wireless voice network and to decompress voice traffic intended fora destination device accessible via a CDMA wireless voice network thatis received via the data network connection 414. In addition, thewireless voice network conversion module may utilize an AdaptiveMulti-Rate Speech Codec (AMR) to compress voice traffic received via aGlobal System for Mobile Communications (GSM) network and to decompressvoice traffic received via the data network connection 414 and intendedfor a destination device accessible via a GSM network.

Additionally, the one or more conversion modules 432 may include awireless data network conversion module that is adapted to compress IPdata received via the fourth network interface 420. The wireless datanetwork conversion module may also decompress IP data received from thedata network connection 414 before forwarding the received IP data to adestination device via the fourth network interface 420.

The routing module 434 is adapted to route voice traffic, data traffic,signaling, or any combination thereof, via the data network connection412, the network interfaces 414-420, or any combination thereof. In aparticular embodiment, the routing module 434 is adapted to receivevoice traffic, data traffic, or any combination thereof, via the datanetwork connection 412, where the voice traffic and/or data traffic isintended for a particular destination device. The destination device maybe accessible via a legacy network or via a DMA server, such as the DMAserver 404 or the additional DMA server 470. The routing module 470 mayidentify the destination device by analyzing routing data associatedwith the voice traffic and/or data traffic. The voice traffic and/ordata traffic received via the data network connection may originate at awireless communication device associated with a DMA server in thecoverage area of the DMAG 404, such as the DMA server 404, theadditional DMA server 470, or any combination thereof.

When the routing data indicates that a particular destination device isaccessible via the landline voice network 422, the routing module 434may be adapted to route voice traffic intended for the particulardestination device via the first network interface 414. In addition,when the routing data indicates that a particular destination device isaccessible via the landline data network 424, the routing module 434 maybe adapted to route voice traffic and/or data traffic intended for theparticular destination device routed via the second network interface416. Further, when the routing data indicates that a particulardestination device is accessible via the wireless voice network 426, therouting module 434 may be adapted to route voice traffic via the thirdnetwork interface 418. Also, when the routing data indicates that aparticular destination device is accessible via the wireless datanetwork 428, the routing module 434 may be adapted to route voicetraffic and/or data traffic via the fourth network interface 420.

Additionally, when the routing data indicates that a particulardestination device is accessible via a DMA server, the routing module434 may be adapted to route voice traffic and/or data traffic via thedata network connection 412. The routing module 434 may identify that adestination device is accessible via a DMA server by comparing adestination device identifier, such as an international mobilesubscriber identification (IMSI), included in the routing data withwireless communication device identifiers included in the register datastore 436. Further, when signaling is required to send voice traffic toa destination device, such as via the landline voice network 422 or thewireless voice network 426, the routing module 434 may be adapted to addsignaling to the voice traffic. The signaling added to the voice trafficmay be utilized by a signaling network associated with the landlinevoice network 422 or the wireless voice network 426, such as an SS7network, to route the voice traffic to a destination device.

The routing module 434 may receive voice traffic, data traffic, or anycombination thereof, via the network interfaces 414-420. After receivingvoice traffic, data traffic, or any combination thereof, via one of thenetwork interfaces 414-420, the routing module 434 may be adapted todetermine a destination device associated with the voice and/or datatraffic. In one embodiment, the routing module 434 may be adapted toidentify a destination device from signaling associated with voicetraffic received from the landline voice network 422 or the wirelessvoice network 426. In an illustrative, non-limiting embodiment, therouting module 434 may utilize global title translation (GTT) toidentify a destination device related to voice traffic received from thelandline voice network 422 or the wireless voice network 426. Further,the routing module 434 may identify a destination device related tovoice traffic associated with a particular wireless communication devicebased on identification information received from an additional DMAG(not shown), where the additional DMAG is adapted to control signalingrelated to voice traffic received from legacy voice networks and theDMAG 402 is adapted to route the corresponding voice traffic receivedfrom the legacy voice networks. In another embodiment, the routingmodule 434 may identify a destination device based on an identifier,such as an IMSI, included in IP data received via the landline datanetwork 424 or the wireless data network 428.

After identifying a destination device related to voice traffic and/ordata traffic received via the network interfaces 414-420, the routingmodule 434 is adapted to determine a routing path for the voice trafficand/or data traffic. The routing module 434 may be determine a routingpath for particular voice traffic and/or data traffic by identifying aDMA server that includes the destination wireless communication devicewithin the coverage area of the identified DMA server. For example, therouting module 434 may be adapted to parse the register data store 436to identify the home location register (HLR) of the respective DMAserver that is designated by a communications service provider to routevoice traffic, data traffic, or any combination thereof, related to thedestination wireless communication device. The routing module 434 may beadapted to determine whether the destination wireless communicationdevice is within the coverage area of the respective DMA server orwithin a coverage area of another DMA server based on the HLR of therespective DMA server. The routing module 434 may then be adapted toroute the voice traffic and/or data traffic to the destination wirelesscommunication device via the appropriate DMA server.

In an illustrative embodiment, the DMAG 404 receives voice traffic andrelated signaling via the first network interface 414. The routingmodule 433 may be adapted to identify a destination wirelesscommunication device, such as the wireless communication device 460, forthe voice traffic from the signaling. After identifying the destinationwireless communication device, the routing module 434 may be adapted toidentify a particular DMA server that includes the wirelesscommunication device 460 within the coverage area of the particular DMAserver. In an example, the routing module 434 may parse HLRs associatedwith each DMA server included in the register data store 438. Therouting module 434 may determine that the wireless communication device460 is included in the HLR of the additional DMA server 470 and that thewireless communication device 460 has roamed into the coverage area ofthe DMA server 404. Thus, the wireless communication device 460 may beincluded in a visitor location register (VLR) associated with the DMAserver 404. Further, the routing module 434 may identify a DMAG that iscontrolling communications related to the DMA server 404. For example,the routing module 434 may parse a home DMA server register of the DMAG402 included in the register data store 438, a visitor DMA serverregister of the DMAG 402 included in the register data store 438, one ormore community DMA registers included in the register data store 438.The routing module 434 may determine that the DMA server 404 is within acommunity DMA register associated with an additional DMAG (not shown)and that the DMA server 404 is included in the visitor DMA serverregister associated with the DMAG 402 indicating that the DMA server hasroamed into the coverage area of the DMAG 402. The routing module 433may then route the voice traffic to the wireless communication device460 along the identified routing path.

The DMA server 404 includes a processor 440 and memory 442. In addition,the DMA server 404 includes a network interface 444 coupled to theprivate IP network 406, a device register 446, and a base transceiverstation (BTS) interface 448. The BTS interface 448 is coupled to one ormore base transceiver stations, such as the base transceiver station 456and the base transceiver station 458. The BTS interface 448 may becoupled to the base transceiver stations 456, 458 via a wirelessconnection or a wireline connection. Each of the base transceiverstations 456, 458 may be adapted to wirelessly transmit and/or receivevoice traffic, data traffic, signaling, or any combination thereof,related to one or more wireless communication devices. For example, thebase transceiver station 456 may transmit and/or receive communicationsrelated to the wireless communication device 460 and the wirelesscommunication device 462 and the base transceiver station 458 maytransmit and/or receive communications related to the wirelesscommunication device 464 and the wireless communication device 466.

The memory 442 includes a coverage module 450, a conversion module 452,and a routing module 454. In one embodiment, each of the modules 430-436can represent instructions that are executable by the processor 408,such as instructions embodied in one or more software programs stored atthe memory 410. In another embodiment, the modules 430-436 can representhardware, software instructions, or any combination thereof.

The device register 446 includes a home location register (HLR) of theDMA server 404, a visitor location register (VLR) of the DMA server 404,one or more community location registers (CLRs) related to one or moreadditional DMA servers, such as the additional DMA server 470, or anycombination thereof. The HLR of the DMA server 404 may include data,such as international mobile subscriber identifications (IMSIs), of oneor more wireless communication devices that are designated by acommunications service provider to communicate voice traffic, datatraffic, signaling, or any combination thereof, via the DMA server 404.The VLR of the DMA server 404 may include data related to one or morewireless communication devices that have roamed into the coverage areaof the DMA server 404. Further, each of the one or more CLRs includesdata related to one or more wireless communication devices that aredesignated by a communications service provider to communicate voicetraffic, data traffic, signaling, or any combination thereof, via anadditional DMA server. For example, the device register 446 may includea CLR having data related to one or more wireless communication devicesthat are designated to transmit and receive communications via theadditional DMA server 470.

In a particular embodiment, the coverage module 450 is adapted toidentify one or more wireless communication devices that are within thecoverage area of the DMA server 404. For example, the coverage module450 may be adapted to send paging signals within the coverage area ofthe DMA server 404 related to requesting identification informationrelated to wireless communication devices that are located within thecoverage area of the DMA server 404. To illustrate, the coverage module450 may transmit an identification information request via the basetransceiver station 456, via the base transceiver station 458, or anycombination thereof, and receive a response from the wirelesscommunication device 460. The response from the wireless communicationdevice 460 may include identification information associated with thewireless communication device, such as an IMSI. After receiving theidentification information from the wireless communication device 460,the coverage module 450 may be adapted to determine if theidentification information of the wireless communication device 460 isincluded in the HLR of the DMA server 404 or within a CLR stored in thedevice register 446. When the identification information of a wirelesscommunication device is included in a CLR stored in the device register446, the coverage module 450 may update the VLR of the DMA server 404 toindicate that the wireless communication device has roamed into thecoverage area of the DMA server 404. The coverage module 450 may alsosend data to the DMAG 402, the additional DMA server 470, or anycombination thereof, indicating that the wireless communication device460 is within the coverage area of the DMA server 404.

The memory 442 also includes a conversion module 452 that is adapted toformat voice traffic, signaling, or any combination thereof, receivedvia the BTS interface 448 according to Internet Protocol (IP). Forexample, the conversion module 452 may receive voice traffic andsignaling from the wireless communication devices 460-466 that areformatted according to CDMA, GSM, or UTMS and the conversion module mayconvert the format of the received voice traffic and signaling to IP. Insome embodiments, the wireless communication devices 460-466 maytransmit voice traffic according to different formats. To illustrate,the wireless communication device 460 may transmit voice trafficaccording to CDMA, the wireless communication device 462 may transmitvoice traffic according to GSM, the wireless communication device 464may transmit voice traffic according to UMTS, and the wirelesscommunication device 466 may transmit voice traffic according to WiMAX.

Additionally, the conversion module 452 is adapted to convert IP datarelated to voice traffic and/or data traffic that is received via thenetwork interface 444 to a format that is recognizable by one or more ofthe wireless communication devices 460-466. For example, the conversionmodule 452 may be adapted to receive voice traffic intended for thewireless communication device 460 via the network interface 444 from theDMAG 402 or the additional DMA server 470 and format the received voicetraffic according to CDMA, GSM, UMTS, or WiMAX depending on the formator formats that can be processed by the wireless communication device460.

The memory 442 includes a routing module 454 adapted to determine arouting path related to voice traffic, data traffic, signaling, or anycombination thereof, received via the BTS interface 448. In a particularembodiment, the routing module 454 receives voice traffic, data traffic,signaling, or any combination thereof, via the BTS interface 448 andidentifies a destination device associated with the receivedcommunications. The routing module 454 may identify a destination deviceassociated with communications received via the BTS interface 448 byparsing the received communications for a destination device identifier.In one example, voice traffic received via the BTS interface 448 may beassociated with signaling that includes an identifier of a destinationdevice, such as an IMSI or a telephone number. In another example, datatraffic received via the BTS interface 448 may include packet dataincluding an identifier related to a destination device.

After identifying a destination device associated with communicationsreceived via the BTS interface 448, the routing module 454 may determinea routing path for the communications to the destination device. In anillustrative embodiment, the routing module 454 may receive voicetraffic from the wireless communication device 460 and determine thatthe voice traffic is intended for a destination device that isaccessible via one of the legacy networks 422-428. For example, therouting module 454 may compare wireless communication deviceidentification information associated with the voice traffic withwireless communication device identification information included in thedevice register 446. When the wireless communication deviceidentification information associated with the voice traffic is notincluded in the device register, the routing module 454 may then beadapted to forward the voice traffic to the DMAG 402 via the networkinterface 444. Further, the routing module 454 may communicate with theDMAG 402 to identify the destination device for the voice traffic. Toillustrate, the routing module 454 may forward wireless communicationdevice identification information associated with the voice traffic tothe DMAG 402 and receive data indicating whether or not the voicetraffic should be routed via the DMAG 402 after the DMAG 402 has parsedthe register data store 438 based on the wireless communication deviceidentification information.

In another illustrative embodiment, the routing module 454 may determinethat voice traffic received from the wireless communication device 460is intended for an additional wireless communication device that isaccessible via the additional DMA server 470. In one example, therouting module 454 may compare wireless communication deviceidentification information associated with the voice traffic withwireless communication device information included in the deviceregister 446 and determine that the wireless communication deviceidentification information is included in a community location registerthat includes wireless communication devices designated to communicatevia the additional DMA server 470 and that the destination wirelesscommunication device is within the coverage area of the additional DMAserver 470. In another example, the routing module 454 may determinethat the destination wireless communication device is included in thehome location register of the DMA server 404, but that the destinationwireless communication device is within the coverage area of theadditional DMA server 470.

The routing module 454 may also determine that voice traffic receivedfrom the wireless communication device is intended for a wirelesscommunication device that is accessible via the DMA server 404, such asthe wireless communication device 464. For example, the routing module454 may compare wireless communication device identification informationassociated with the voice traffic to wireless communication deviceidentification information included in the device register 446 anddetermine that the wireless communication device 464 is included in thehome location register of the DMA server 404 or in the visitor locationregister of the DMA server 404.

Additionally, the routing module 454 may receive data traffic via theBTS interface 448 and identify a destination device related to the datatraffic. In one embodiment, the routing module 454 may identify adestination device related to the data traffic that is accessible viathe landline data network 424 or the wireless data network 428 and thenforward the data traffic to the DMAG 402. For example, the routingmodule 454 may identify the destination device related to the datatraffic based on a destination IP address included in the data trafficor a destination device IMSI included in the data traffic, or anycombination thereof. In another embodiment, the routing module 454 maydetermine that the data traffic is intended for a destination devicethat is accessible via the additional DMA server 470 or the DMA server404 by parsing the device register 446 for the destination deviceidentification information.

Further, the routing module 454 may receive packet data related to voicetraffic, data traffic, signaling, or any combination thereof, from theDMAG 402, the additional DMA server, or any combination thereof, via thenetwork interface 444. The routing module 454 may be adapted to identifya destination wireless communication device by comparing wirelesscommunication device identification information associated with thepacket data with wireless communication device identificationinformation included in the device register 446. For example, therouting module 454 may determine that packet data received via thenetwork interface 444 is intended for the wireless communication device460 based on an IMSI included in the packet data. After identifying thedestination wireless communication device associated with the packetdata, the routing module 454 may parse the device register 446 todetermine a location of the destination wireless communication deviceand transmit the packet data to the destination wireless communicationdevice via a base transceiver station that is adapted to communicatewith the destination wireless communication device. To illustrate, therouting module 454 may determine that packet data is intended for thewireless communication device 460 and that the wireless communicationdevice 460 is within range to communicate via the base transceiverstation 456. The routing module 454 may then be adapted to route havethe voice traffic, data traffic, or any combination thereof, related tothe packet data to the wireless communication device 460 via the basetransceiver station 456.

FIG. 5A is a diagram of a particular embodiment of a home distributedmobile architecture (DMA) server register 502. The home DMA serverregister 502 may be associated with a particular distributed mobilearchitecture gateway (DMAG). The home DMA server register 502 includesinformation related to one or more DMA servers that have been designatedby a communications service provider to send and receive voice traffic,data traffic, signaling, or any combination thereof, via the particularDMAG. The home DMA server register 502 includes information related to afirst DMA server at 510, information related to a second DMA server at512, and information related to a third DMA server at 514.

At 504, the home DMA server register 502 may include identificationinformation, such as an IP address, associated with each DMA serverincluded in the home DMA server register 502. Additionally, at 506, thehome DMA server register 502 may include a home location register (HLR)of each DMA server included in the home DMA server register 502. EachHLR may include information related to one or more wirelesscommunication devices designated by a communications service provider tosend and receive communications via the DMA server associated with therespective HLR. For example, the HLR of the first DMA server includesinformation related to each of the wireless communication devicesdesignated by the communications service provider to send and receivecommunications via the first DMA server. Further, at 508, the home DMAserver register 502 may include a visitor location register (VLR) ofeach DMA server included in the home DMA server register 502. Each VLRmay include information related to one or more wireless communicationdevices that have roamed into the coverage area of the respective DMAserver. Although the home DMA server register 502 is shown includinginformation related to three DMA servers, the home DMA server register502 may include information related to various numbers of DMA servers.Additionally, the home DMA server register 502 may include furtherinformation related to each DMA server, such as whether or not aparticular DMA server is roaming with respect to the DMAG associatedwith the home DMA server register.

FIG. 5B is a diagram of a particular embodiment of a visitor distributedmobile architecture (DMA) server register 520. The visitor DMA serverregister 520 may be associated with a particular distributed mobilearchitecture gateway (DMAG). The visitor DMA server register 520includes information related to one or more DMA servers that have beendesignated by a communications service provider to send and receivevoice traffic, data traffic, signaling, or any combination thereof, viaa DMAG other than the particular DMAG associated with the visitor DMAserver register 520 and that have roamed into the coverage area of theparticular DMAG. The visitor DMA server register 520 includesinformation related to a DMA server a at 528, information related to aDMA server b at 530, and information related to a DMA server c at 532.

At 522, the visitor DMA server register 520 may include identificationinformation, such as an IP address, associated with each DMA serverincluded in the visitor DMA server register 520. Additionally, at 524,the visitor DMA server register 520 may include a home location register(HLR) of each DMA server included in the visitor DMA server register520. Each HLR may include information related to one or more wirelesscommunication devices designated by a communications service provider tosend and receive communications via the DMA server associated with therespective HLR. Further, at 526, the visitor DMA server register 520 mayinclude a visitor location register (VLR) of each DMA server included inthe visitor DMA server register 520. Each VLR may include informationrelated to one or more wireless communication devices that have roamedinto the coverage area of the respective DMA server. Although thevisitor DMA server register 520 is shown including information relatedto three DMA servers, the visitor DMA server register 520 may includeinformation related to various numbers of DMA servers.

FIG. 5C is a diagram of a particular embodiment of a communitydistributed mobile architecture (DMA) server register 540. A particularDMAG may include a community DMA server register 540 that includesinformation related to DMAGs other than the particular DMAG thatincludes the community DMA server register 540. For example, thecommunity DMA server register 540 includes information related to afirst DMAG at 552, information related to a second DMAG at 554, andinformation related to a third DMAG at 556. At 542, the community DMAserver register 540 includes an identifier associated with each DMAG ofthe community DMA server register 540, such as an IP address. At 544,the community DMA server register 540 includes a home DMA serverregister related to each DMAG of the community DMA server register 540,such as the home DMA server register 502 of FIG. 5A. In addition, at546, the community DMA server register 540 includes a visitor DMA serverregister related to each DMAG of the community DMA server register 540,such as the visitor DMA server register 520 of FIG. 5B. Further, at 548,the community DMA server register 540 includes an HLR associated witheach DMA server that is included in the coverage area of the respectiveDMAG, an HLR associated with each DMA server that is designated by acommunications service provider to communicate via the respective DMAG,or any combination thereof. At 550, the community DMA server register540 includes a VLR associated with each DMA server that is included inthe coverage area of the respective DMAG, a VLR associated with each DMAserver that is designated by a communications service provider tocommunicate via the respective DMAG, or any combination thereof.Although the community DMA server register 540 is shown includinginformation related to three DMAGs, the community DMA server register540 may include information related to various numbers of DMAs.

FIG. 6 is a flow diagram of a method of controlling wirelesscommunications. At 602, a distributed mobile architecture gateway (DMAG)receives voice traffic via a legacy communication network, such as alandline voice network or a wireless voice network. The voice traffic isintended for a wireless communication device that is accessible via aDMA server. Proceeding to 604, the DMAG converts the voice traffic topacket data formatted according to Internet Protocol (IP). Moving to606, the DMAG identifies the particular DMA server that is associatedwith a coverage area that includes the wireless communication device.The particular DMA server may be located within a coverage area of theDMAG. The DMAG may identify the particular DMA server by parsing adatabase that includes a list of wireless communication devicesregistered with each DMA server in the coverage area of the DMAG. Thedatabase may include a home DMA server register, a visitor DMA serverregister, a community DMA server register, or any combination thereof.Advancing to 608, the DMAG sends the IP packet data related to the voicetraffic to the identified DMA server. The method terminates at 610.

FIG. 7 is a flow diagram of a second embodiment of a method ofcontrolling wireless communications. At 702, a distributed mobilearchitecture (DMA) server receives an identification information requestfrom a distributed mobile architecture gateway (DMAG) when the DMAserver moves into a coverage area of the DMAG. Proceeding to 704, theDMA server sends identification information related to the DMA server,such as an IP address, to the DMAG. Moving to 706, the DMA serverreceives voice traffic from a wireless communication device located inthe coverage area of the DMA server.

Advancing to 708, the DMA server converts the voice traffic receivedfrom the wireless communication device to packet data formattedaccording to Internet Protocol (IP). At 710, the DMA server sends the IPpacket data related to the voice traffic to the DMAG. The voice trafficmay be intended for a destination device accessible via a legacycommunication network, a destination device accessible via an additionalDMA server, or a destination device accessible with the DMA server. Themethod terminates at 712.

Referring to FIG. 8, a fifth embodiment of a system to control wirelesscommunications is shown and is generally designated 800. As shown, thesystem 800 includes a distributed mobile architecture gateway (DMAG) 802that is connected to a wireless carrier's central mobile switchingcenter (MSC) 804. The DMAG 802 may include a DMAG shown in FIGS. 1-4.The DMAG 802 can be connected to the MSC 804 via an E1 common channelsignaling (CCS) connection (e.g. G.703, G.732), or any other applicableconnection. The MSC 804, in turn, is connected to a code divisionmultiple access (CDMA) network 806. FIG. 8 further shows that the DMAG802 can be connected to a switching transfer point (STP) 808 of astand-alone carrier. As shown, the DMAG 802 can be connected to the STP808 via an IS-41+IS-880 (DS0) connection, or an ISUP internetworkingtransfer unit (ITU) N7 connection.

As further depicted in FIG. 8, the STP 808 can be connected to a shortmessaging service (SMS) server 810 in order to provide text-messagingcapabilities for the mobile communication devices using the system 800shown in FIG. 8. Additionally, the STP 808 can be connected to a homelocation register (HLR) 812, a pre-paid wireless server 814 and aninternational roaming network 816 in order to provide pre-paid servicesand roaming between multiple countries. FIG. 8 shows that the DMAG 802can be connected to the PTSN 818 via an E1 CCS (G.703, G.732)connection, or any other appropriate connection.

FIG. 9 is a sixth embodiment of a system 900 to control wirelesscommunications. As shown, the system 900 includes a city area coveragesite 902 and an urban fringe/nearby village coverage site 904. In anexemplary, non-limiting embodiment, the city area coverage site 902includes a first mobile switching center/base station controller(MSC/BSC) center 906 connected to a second MSC/BSC center 908. Also, afirst representative base transceiver station (BTS) 910 and a secondrepresentative BTS 912 are connected to the first MSC/BSC center 906.The particular deployment of equipment is configured to provide adequatecellular coverage for mobile communication devices within the city areacoverage site 902.

As illustrated in FIG. 9, the urban fringe/nearby village coverage site904 includes a DMA server 914 having a plurality of BTSs 916 connectedthereto. The distributed mobile architecture gateway (DMAG) 914 canprovide hand-off of calls between the BTSs 916 and can switch calls madebetween the BTSs 916 locally. However, the DMAG 914 within the urbanfringe/nearby village coverage site 904 can also connect telephonytraffic to the first MSC/BSC center 906 within the city area coveragesite 902 via a data network connection 918. In one embodiment, the datanetwork connection can be an E1 connection, a T1 connection, a microwaveconnection, or an 802.11 connection established via an IS-41 subset orMAP subset. The deployment of a DMAG 914 in a location such as thatdescribed above, i.e., in urban fringe or in a nearby village, and theconnection of the DMAG 914 to an MSC/BSC center 906 in a city area, canprovide service to potential wireless customers that typically would notreceive cellular coverage from the city area cellular coverage site 902.Thus, new subscribers receive access to wireless communication serviceand can further communicate with wireless customers within the city areacellular coverage site 902.

FIG. 10 is a seventh embodiment of a system 1000 to control wirelesscommunications. As depicted in FIG. 10, the system 1000 includes adistributed mobile architecture gateway (DMAG) 1002 and a distributedmobile architecture (DMA) server 1004 that is connected to a basetransceiver station (BTS) 1006. The BTS 1006, in turn, is connected toan antenna 1008. FIG. 10 further illustrates that a first satellitetransceiver 1010 is also connected to the DMAG 1002. The first satellitetransceiver 1010 communicates with a second satellite transceiver 1012via a satellite 1014. Additionally, the second satellite transceiver1012 includes a data network connection 1016, e.g., a T1 connection, oran E1 connection. The satellite transceivers 1010, 1012 and thesatellite 1014 can provide a backhaul connection for the DMAG 1002 orthe satellite transceivers 1010, 1012 and the satellite 1014 can connectthe DMAG 1002 to an additional DMAG (not shown).

FIG. 11 is an eighth embodiment of a system 1100 to control wirelesscommunications. As shown, the system 1100 includes a distributed mobilearchitecture gateway (DMAG) 1102 having a primary network connection1104 and a distributed mobile architecture (DMA) server 1106. Moreover,the DMAG 1102 can be connected to a plurality of interworking units(IWUs) 1108, 1116, 1124. In an exemplary, non-limiting embodiment, theDMAG 1102 can be connected to each IWU 1108, 1116, 1124 via a respectivesecondary network connection 1110, 1118, 1126, such as a category five(Cat 5) cable connection, a microwave connection, or a WLAN connection.Further, each IWU 1108, 1116, 1124 is connected to a respective basetransceiver station (BTS) 1112, 1120, 1128 and each BTS, in turn, isconnected to a respective antenna 1114, 1122, 1130. Each BTS 1114, 1122,1130 can be a 3-sector BTS. In the deployment depicted in FIG. 11, theDMAG 1102 can act as a centralized micro-switch that can be used tohandle telephony traffic received at the antennae 1114, 1122, 1130.

FIG. 12 is a ninth embodiment of a system 1200 to control wirelesscommunications. As depicted, the system 1200 includes a plurality ofmobile cellular coverage sites 1230, 1232. Each mobile cellular coveragesite 1230, 1232 includes a respective vehicle 1206, 1216 in which afield distributed mobile architecture (DMA) server 1208, 1218 isdisposed. Moreover, a respective base transceiver station (BTS) 1210,1220 is disposed within each vehicle 1206, 1216 and is in directphysical connection with the field DMA servers 1208, 1218, e.g., by awire or cable connected there between. The field DMA servers 1208, 1218and the BTSs 1210, 1220 can be removably installed within the vehicles1206, 1216 or permanently affixed therein. FIG. 12 further indicatesthat each BTS 1210, 1220 can include a respective antenna 1212, 1222that is designed to communicate with mobile communication devices. Also,each field DMA server 1208, 1218 includes a respective antenna 1214,1224. In an exemplary, non-limiting embodiment, the field DMA servers1208, 1218 can communicate wirelessly with each other via the antennae1212, 1222, e.g., via 802.11a, 802.11b, microwaves, or other wirelesslink.

The mobile cellular coverage sites 1230, 1232 can be deployed to providea temporary web of cellular coverage for a plurality of mobilecommunication devices, e.g., devices carried by soldiers during abattle. The mobile in-field communications system 1200 can be recalled,moved, and re-deployed as necessary. Further, the system can include awireless connection, e.g., 802.11a, 802.11b, microwaves, to thedistributed mobile architecture gateway (DMAG) 1204 that is adapted toroute communications to and from the legacy networks 1202.

FIG. 13 is a tenth embodiment of a system to control wirelesscommunications. FIG. 13 depicts a structure 1302, e.g., an officebuilding, a commercial building, a house, etc. An enterprise local areanetwork (LAN) 1304 is installed within the building 1302. A micro-BTS1308 is connected to the enterprise LAN 1304. Moreover, a voice mailserver 1324 and plural enterprise services servers 1326 are connected tothe enterprise LAN 1304. In an exemplary, non-limiting embodiment, theenterprise services servers 1326 can include a dynamic hostconfiguration protocol (DHCP) server, a radius server, a domain nameserver (DNS), etc. As depicted in FIG. 13, a plurality of phones 1328,e.g., IP desk phones, can be connected to the enterprise LAN 1304.

FIG. 13 further indicates that an office DMA server 1306 can beconnected to the enterprise LAN 1304. The office DMA server 1306 canalso be connected to a distributed mobile architecture gateway (DMAG)1310 that is coupled to the PSTN 1312. The PSTN 1312 can, in turn, canbe connected to a cellular voice and data network 1314. The enterpriseLAN 1304 can also be connected to the cellular voice and data network1314 via an Internet protocol (IP) network 1318. A signaling systemseven (SS7) network 1316 can be connected to the cellular voice and datanetwork 1314 and the IP network 1318. FIG. 13 also depicts an SS7gateway 1320 between the SS7 network 11316 and the IP network 1318.Further, FIG. 13 includes a firewall 1322 between the enterprise LAN1304 and the IP network 1318. FIG. 13 shows a wireless communicationdevice 1328 in communication with the cellular voice and data network1314 and the micro-BTS 1308.

With the configuration of structure described above, the presentdisclosure provides a system and method of controlling wirelesscommunications through use of flexible telecommunications devices, suchas the DMA servers and DMAGs shown in FIGS. 1-4 and FIGS. 9-14, that aredistributive and associative. That is, the DMA servers and DMAGs canoperate stand-alone or seamlessly within an existing cellular or othernetwork. The DMA servers can be integrated with virtually any thirdparty base station. The DMA servers, the DMAGs, or any combinationthereof, can provide integrated prepaid billing, OAMP, networkmanagement, and AAA functionality. The DMA server and/or the DMAG caninclude a Java based user interface and feature configuration system andcan provide real time call metering, call detail record (CDR)generation, and real time call provisioning. The DMA server may beimplemented in a relatively small footprint, such as a footprint thesize of a laptop computer, and has a relatively low power requirement.Further, the DMA server and DMAG may be implemented using inexpensiveand widely available computer equipment.

With one or more of the deployment configurations described above, thepresent system provides mobile to landline calls via a DMAG from mobilehandsets within a DMA server cellular coverage area. Also, mobile tolandline calls via a DMAG can be made from mobile handsets roaming intoDMA coverage areas. Mobile to mobile calls can be made from home/roaminghandsets to DMA handsets and vice versa. Further, mobile to IP calls andIP to mobile calls can be made from within a DMA server coverage area.IP to IP calls can be made from any DMA handset to any IP phone.Additionally, IP to landline calls and landline to IP calls can be madefrom a DMA handset to any phone. Further, land-line to mobile calls toDMA handsets can be made.

The systems described above can support call forwarding, call waiting,3-way calling caller ID, voice mail, and mobile to mobile SMS service,i.e., text messaging. Further, the systems described above can providebroadcast SMS service, mobile to land high-speed IP data (1X or GPRS)service and mobile-to-mobile high speed IP data (1X or GPRS) service.Also, the systems described above can provide IP-PBX capability.

Associated systems can be redundant, self-healing, self-organizing, andscalable. Distributed systems can be “snap-together,” i.e., a DMA servercan be linked to a previously deployed DMA server and a DMAG can beadded to an addition DMAG in order to broaden, or otherwise extend,cellular coverage. Further, distributed systems can be de-centralized toavoid single points of failure.

One or more of the systems described above can also provide soft andsofter call handoffs on the same frequency interfaces. Also, softhandoffs can be provided on different systems. Further, a DMA basedsystem can operate stand-alone with a billing system provided by a DMAserver and CDR generation. Alternatively, a system can use the SS7network to pass CDRs to a central switch for integrated billing andoperation with an existing network.

The above-disclosed subject matter is to be considered illustrative, andnot restrictive, and the appended claims are intended to cover all suchmodifications, enhancements, and other embodiments, which fall withinthe true spirit and scope of the present invention. Thus, to the maximumextent allowed by law, the scope of the present invention is to bedetermined by the broadest permissible interpretation of the followingclaims and their equivalents, and shall not be restricted or limited bythe foregoing detailed description.

What is claimed is:
 1. A method of routing calls via a communicationsnetwork, the method comprising: receiving first traffic at a firstdistributed mobile architecture (DMA) server from a first wirelesscommunication device via a base transceiver station integrated with thefirst DMA server, the first traffic including voice traffic, datatraffic, or a combination thereof, wherein the first DMA server isadapted to receive the first traffic while the first DMA server is beingtransported by a vehicle from a first location to a second location; andforwarding first packet data related to the first traffic over a privateinterne protocol (IP) network to a distributed mobile architecturegateway (DMAG), wherein the first traffic is directed to a destinationdevice that is accessible via a legacy communication network.
 2. Themethod of claim 1, further comprising receiving second packet datarelated to second traffic at the first DMA server from the DMAG via theprivate IP network, the second traffic including second voice traffic,second data traffic, or a combination thereof, Wherein the second voicetraffic is directed to the first wireless communication device from asecond wireless communication device, wherein the first wirelesscommunication device is within a coverage area of the first DMA serverand the second wireless communication device is within a second coveragearea of a second DMA server.
 3. The method of claim 2, wherein the firstDMA server and the second DMA server are designated by a communicationsservice provider to route communications related to the legacycommunication network via the DMAG.
 4. The method of claim 2, whereinthe DMAG is coupled to a second DMAG via the private IP network.
 5. Themethod of claim 1, wherein the legacy communication network comprises acellular network and the DMAG is coupled to the legacy communicationnetwork.
 6. The method of claim 1, wherein the DMAG includes a communityserver register.
 7. The method of claim 1, wherein the DMAG isassociated with a service area and the first DMA server is located withthe service area.
 8. The method of claim 7, wherein the DMAG isconfigured to route voice traffic, data traffic, or a combinationthereof associated with other DMA servers that roam into the servicearea.
 9. A network communication system, comprising: a distributedmobile architecture (DMA) server coupled to a base transceiver station,the DMA server including: a routing module adapted to: receive firsttraffic via a legacy communication network, wherein the first traffic isdirected to a wireless communication device within a coverage area ofthe DMA server, the first traffic including voice traffic, data traffic,or a combination thereof, wherein the DMA server is adapted to receivethe first traffic while the DMA server is being transported by a vehiclefrom a first location to a second location; receive first signalinginformation related to the first traffic from a distributed mobilearchitecture gateway (DMAG) via, a private Internet Protocol (IP)network; and route the first traffic to the wireless communicationdevice via the base transceiver station according to the first signalinginformation.
 10. The system of claim 9, wherein the DMA server iscoupled to the base transceiver station via an interworking unit. 11.The system of claim 9, wherein the DMA server is located within astructure and is coupled to an enterprise, local area network locatedwithin the structure.
 12. The system of claim 11, wherein the DMAG islocated outside the structure and is coupled to a public switchedtelephone network (PSTN).
 13. The system of claim 9, wherein the routingmodule is adapted to: receive packet data related to second traffic andsecond signaling information related to the second traffic from theDMAG, the second traffic including second voice traffic, second datatraffic, or a combination thereof, wherein the second traffic isdirected to the wireless communication device; and route the secondtraffic to the wireless communication device via the base transceiverstation according to the second signaling information.
 14. The system ofclaim 9, wherein the legacy communication network is a cellular networkand the DMAG is coupled to the legacy communication network.
 15. Thesystem of claim 9, wherein the legacy communication network is awireline network.
 16. The system of claim 9, wherein the legacycommunication network includes a wireline network and a wirelessnetwork.
 17. The system of claim 9, wherein the DMAG includes acommunity server register.
 18. The system of claim 9, wherein the DMAGis coupled to a second DMAG via a private network.
 19. A networkcommunication system, comprising: a plurality of distributed mobilearchitecture gateways, each distributed mobile architecture gatewayincluding at least one interface to communicate with one or more legacycommunication networks and each distributed mobile architecture gatewayincluding a data network connection, the data network connection adaptedto connect to at least one other distributed mobile architecture gatewayof the plurality of distributed mobile architecture gateways; and aprivate Internet Protocol (IP) network connecting each distributedmobile architecture gateway to a respective set of distributed mobilearchitecture (DMA) servers, each DMA server coupled to a respective basetransceiver station, wherein the private IP network also connects eachDMA server in a particular set of DMA servers to the DMA servers in theother sets of DMA servers, and wherein a first DMA server coupled to aparticular distributed mobile architecture gateway is adapted to receivetraffic while the first DMA server is being transported by a vehiclefrom a first location to a second location, the traffic including voicetraffic, data traffic, or a combination thereof.
 20. The system of claim19, wherein at least one of the one or more legacy networks is acellular network.